home *** CD-ROM | disk | FTP | other *** search
/ SGI Performance Co-Pilot 1.3 / SGI Performance Co-Pilot 1.3.iso / dist / dist6.4 / pcp.idb / usr / share / catman / u_man / cat1 / pmvcr.z / pmvcr
Text File  |  1997-04-03  |  5KB  |  133 lines
  1.  
  2.  
  3.  
  4. PPPPMMMMVVVVCCCCRRRR((((1111))))                                                              PPPPMMMMVVVVCCCCRRRR((((1111))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      ppppmmmmvvvvccccrrrr - Performance Co-Pilot VCR mode server for the PMCD
  10.  
  11. SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  12.      ppppmmmmvvvvccccrrrr [----rrrr _r_e_q_f_d] [_p_m_c_d-_o_p_t_i_o_n_s]
  13.  
  14. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  15.      ppppmmmmvvvvccccrrrr is the VCR mode server that implements the playback services of the
  16.      Performance Metrics Collector Daemon, ppppmmmmccccdddd(1), within the Performance
  17.      Co-Pilot (PCP) framework.
  18.  
  19.      On a system where there is an instance of ppppmmmmccccdddd(1) running, there may be
  20.      an associated instance of ppppmmmmvvvvccccrrrr that is launched by ppppmmmmccccdddd(1), if, and only
  21.      if, it is required.  This is the only way that ppppmmmmvvvvccccrrrr should be launched,
  22.      and under no circumstances will it be helpful to launch ppppmmmmvvvvccccrrrr either
  23.      interactively, or from a script.
  24.  
  25.      When clients of the associated ppppmmmmccccdddd(1), make requests to retrieve the
  26.      values of performance metrics from the recent past, these requests are
  27.      intercepted below the Performance Metrics Application Programming
  28.      Interface (PMAPI) in the client, and are forwarded directly to ppppmmmmvvvvccccrrrr.
  29.      For each client, the first such request involves establishing a TCP/IP
  30.      socket with ppppmmmmvvvvccccrrrr, and ppppmmmmvvvvccccrrrr accepts these incoming connection requests
  31.      on the file descriptor _r_e_q_f_d specified with the ----rrrr option.  ppppmmmmvvvvccccrrrr
  32.      responds directly to the requesting client.
  33.  
  34.      The _p_m_c_d-_o_p_t_i_o_n_s are all of the options specified when ppppmmmmccccdddd(1) was
  35.      started, and these are passed directly to ppppmmmmvvvvccccrrrr.
  36.  
  37.      All information returned by ppppmmmmvvvvccccrrrr is actually obtained from the archives
  38.      maintained by the system instance of the PCP logger program, ppppmmmmllllooooggggggggeeeerrrr(1).
  39.  
  40. FFFFIIIILLLLEEEESSSS
  41.      ....////ppppmmmmvvvvccccrrrr....lllloooogggg         (or $$$${{{{PPPPCCCCPPPP____LLLLOOOOGGGGDDDDIIIIRRRR----////vvvvaaaarrrr////aaaaddddmmmm////ppppccccpppplllloooogggg}}}}////ppppmmmmvvvvccccrrrr....lllloooogggg when
  42.                          ppppmmmmccccdddd(1) has been started automatically from
  43.                          ////eeeettttcccc////iiiinnnniiiitttt....dddd////ppppccccpppp)
  44.                          All error messages and diagnostics are directed here.
  45.  
  46. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  47.      ppppmmmmccccdddd(1), ppppmmmmllllooooggggggggeeeerrrr(1), PPPPMMMMAAAAPPPPIIII(3) and ppppmmmmSSSSeeeettttMMMMooooddddeeee(3).
  48.  
  49. CCCCAAAAVVVVEEEEAAAATTTTSSSS
  50.      The original intent was to support seamless VCR-replay between a current
  51.      ``live'' source and a recently created archive source.
  52.  
  53.      In practise, the semantic and operational difficulties associated with
  54.      transitions between ``live'' and ``archive'' modes are so significant
  55.      that the feature has never been fully implemented, and is likely to be
  56.      withdrawn from future PCP releases.
  57.  
  58.  
  59.  
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70. PPPPMMMMVVVVCCCCRRRR((((1111))))                                                              PPPPMMMMVVVVCCCCRRRR((((1111))))
  71.  
  72.  
  73.  
  74.      The services provided by ppppmmmmvvvvccccrrrr are not used by any PCP utility or tool.
  75.  
  76. DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
  77.      The PCP debug control flag DDDDBBBBGGGG____TTTTRRRRAAAACCCCEEEE____AAAAPPPPPPPPLLLL0000 (see ppppmmmmddddbbbbgggg(1)) may be
  78.      specified via a ----DDDD option to ppppmmmmccccdddd(1) and hence ppppmmmmvvvvccccrrrr - this will cause
  79.      assorted diagnostics specific to the operation of ppppmmmmvvvvccccrrrr to appear in the
  80.      diagnostic log file.
  81.  
  82.  
  83.  
  84.  
  85.  
  86.  
  87.  
  88.  
  89.  
  90.  
  91.  
  92.  
  93.  
  94.  
  95.  
  96.  
  97.  
  98.  
  99.  
  100.  
  101.  
  102.  
  103.  
  104.  
  105.  
  106.  
  107.  
  108.  
  109.  
  110.  
  111.  
  112.  
  113.  
  114.  
  115.  
  116.  
  117.  
  118.  
  119.  
  120.  
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127.  
  128.  
  129.                                                                         PPPPaaaaggggeeee 2222
  130.  
  131.  
  132.  
  133.